Encryption key updating for multiple site automated login

ABSTRACT

A version number is associated with an encrypted key executable to allow real time updating of keys for a system which facilitates users signing on to multiple websites on different domains using an encrypted ticket. Two keys may be used at each site during updating of keys, each having an associated one digit Hex version tag. When a key is to be updated with a new key, the existing or old key is provided an expiration time. A second key is provided from the system in a secure manner with a new version number and made the current key which provides decryption of the encrypted ticket. The system tracks both keys while they are concurrent. After the existing key expires, only the second, or updated key is used to provide login services for users. The system periodically flushes old keys.

RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 09/594,304, filed on Jun. 15, 2000, the disclosureof which is incorporated by reference herein.

FIELD OF THE INVENTION

This invention relates generally to the field of computers, and inparticular to automatically updating keys used to log into multiplesites.

COPYRIGHT NOTICE/PERMISSION

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in the drawing hereto: Copyright© 2000, MicrosoftCorporation, All Rights Reserved.

BACKGROUND

The recent growth in popularity of the Internet has significantlyincreased the number of Internet users and the number of Internet sites(also referred to as “web sites”). Web sites may provide various typesof information to users, offer products or services for sale, andprovide games and other forms of entertainment. Many web sites requireusers to “register” by providing information about themselves before theweb server grants access to the site. This registration information mayinclude the user's name, account number, address, telephone number,email address, computer platform, age, gender, or hobbies. Theregistration information collected by the web site may be necessary tocomplete transactions (such as commercial or financial transactions).Additionally, information can be collected which allows the web siteoperator to learn about the visitors to the site to better target itsfuture marketing activities or adjust the information provided on theweb site. The collected information may also be used to allow the website to contact the user directly (e.g., via email) in the future toannounce, for example, special promotions, new products, or new featuresof the web site.

When registering with a web site for the first time, the web sitetypically requests that the user select a login ID and an associatedpassword. The login ID allows the web site to identify the user andretrieve the user's information during subsequent user visits to the website. Generally, the login ID must be unique to the web site such thatno two users have the same login ID. The password associated with thelogin ID allows the web site to authenticate the user during subsequentvisits to the web site. The password also prevents others (who do notknow the password) from accessing the web site using the user's loginID. This password protection is particularly important if the web sitestores private or confidential information about the user, such asfinancial information or medial records.

If a user visits several different web sites, each web site may requireentry of similar registration information about the user, such as theuser's name, mailing address, and email address. This repeated entry ofidentical data is tedious when visiting multiple web sites in a shortperiod of time. Many web sites require the user to register beforeaccessing any information provided on the web site. Thus, the user mustenter the requested registration information before they can determinewhether the site contains any information of interest.

After registering with multiple web sites, the user must remember thespecific login ID and password used with each web site or other Internetservice. Without the correct login ID and password, the user mustre-enter the registration information. A particular user is likely tohave different login IDs and associated passwords on different websites. For example, a user named Bob Smith may select “smith” as hislogin ID for a particular site. If the site already has a user with alogin ID of “smith” or requires a login ID of at least six characters,then the user must select a different login ID. After registering atnumerous web sites, Bob Smith may have a collection of different loginIDs, such as: smith, smith1, bsmith, smithb, bobsmith, bob_smith, andsmithbob. Further, different passwords may be associated with differentlogin IDs due to differing password requirements of the different websites (e.g., password length requirements or a requirement that eachpassword include at least one numeric character). Thus, Bob Smith mustmaintain a list of web sites, login IDs, and associated passwords forall sites that he visits regularly.

Some sites keep track of this login information for the user, andprovide a key ring, which is essentially set of images or icons whichwhen selected provide login information to a site associated.

There is a need for a secure way to log in to multiple sites. There is afurther need to be able to change security parameters on sites withoutinterrupting the user or site. There is yet a further need to managesecurity for multiple sites in a multiple site login service in a simpleand uncomplicated manner.

SUMMARY OF THE INVENTION

New keys for decrypting automatic login information are distributed, andmay coexist with a current key. Following a selected time, the new keybecomes the current key.

During the period of coexistence of keys, a multiple site login servicewhich issues the tickets begins to send tickets to the sites which maybe decrypted by use of the new key. Following a period of time at leastas long as the coexistence period, the old keys are expired and nolonger available for use. A configuration file is used to keep track ofsites logged into as well as a login ID and password for each site. As asite is visited by the user, the ticket is created from thisinformation. Each key has a version tag associated with it. When anupdated key is issued by the login service, the version tag isincremented or otherwise changed.

The site usually has a predetermined reauthorization period, after whicheach user is required to reauthenticate to the site again. The loginservice provides the ticket again for reauthorization. By setting theselected time for the new key to become the current key, all userscurrently logged into a site will not see a difference in operation. Bythe time the selected time passes, all users logged into the site willhave already reauthorized using a ticket corresponding to the new key.

An individual site may request a new key, as may the login service. Inone aspect of the invention, the login service generates a new key for asite to ensure that a minimum level of security of the site ismaintained.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing pertinent components of a computer inaccordance with the invention.

FIG. 2 illustrates an exemplary network environment in which the presentinvention is utilized.

FIG. 3 is a block diagram showing components involved in key generation,distribution, updating and use.

DETAILED DESCRIPTION

In the following detailed description of exemplary embodiments of theinvention, reference is made to the accompanying drawings which form apart hereof, and in which is shown by way of illustration specificexemplary embodiments in which the invention may be practiced. Theseembodiments are described in sufficient detail to enable those skilledin the art to practice the invention, and it is to be understood thatother embodiments may be utilized and that logical, mechanical,electrical and other changes may be made without departing from thespirit or scope of the present invention. The following detaileddescription is, therefore, not to be taken in a limiting sense, and thescope of the present invention is defined only by the appended claims.

The detailed description is divided into multiple sections. A firstsection describes a simple representation of a computer system and theoperation of multiple computer systems on a network which implementdifferent aspect of the current invention. This is followed by adescription of the invention and how it is implemented.

HARDWARE AND OPERATING ENVIRONMENT

An exemplary system for implementing the invention includes a computingdevice, such as computing device 100 in FIG. 1. In its most basicconfiguration, computing device 100 typically includes at least oneprocessing unit 102 and memory 104. Depending on the exact configurationand type of computing device, memory 104 may be volatile (such as RAM),non-volatile (such as ROM, flash memory, etc.) or some combination ofthe two. This most basic configuration is illustrated in FIG. 1 bybroken line 106.

Device 100 may also include additional features/functionality. Forexample, device 100 may include additional storage (removable and/ornon-removable) including, but not limited to, magnetic or optical disksor tape. Such additional storage is illustrated in FIG. 1 by removablestorage 108 and non-removable storage 110. Computer-readable nontransitory storage media includes volatile and nonvolatile, removableand non-removable media implemented in any method of technology forstorage of information such as computer readable instructions, datastructures, program modules or other data. Memory 104, removable storage108 and non-removable storage 110 are all examples of computer-readablenon transitory storage media. Computer-readable non transitory storagemedia includes, but is not limited to RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic based storage or any other non transitorymedium which can be used to store desired information and which can beaccessed by device 100. Any such computer-readable non transitorystorage media may be part of device 100.

Device 100 may also contain communications connection(s) 112 that allowthe device to communicate with other devices. Communicationsconnection(s) 112 is an example of communication media. Communicationsmedia typically embodies computer readable instructions, datastructures, program modules or other data in a modulated data signalsuch as a carrier wave or other transport mechanism and includes anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set of changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such aswired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. The term computerreadable media as used herein includes both computer-readable nontransitory storage media and communications media.

Device 100 may also have input device(s) 114 such as keyboard, mouse,pen, voice input device, touch input device, etc. Output device(s) 116such as display, speakers, printers, etc may also be included. All thesedevices are well known in the art.

This invention may be described in the context of computer-executableinstructions, such as program modules, executed by one or more computeror other devices such as device 110. Generally, program modules includeroutines, programs, objects, components, data structures, etc. thatperform particular tasks or implement particular abstract data types.Typically the functionality of the program modules may be combined ordistributed as desired in various embodiments.

FIG. 2 is a block diagram illustrating an exemplary network environmentin which the present invention is utilized. A client computer system 200is coupled to a network 202. In this example, network 202 is theInternet (or the World-Wide Web). However, the teachings of the presentinvention can be applied to any data communication network thatimplements a stateless protocol similar to hypertext transfer protocol,http. Multiple affiliate servers 204, 206, and 208 are coupled tonetwork 202, thereby allowing client computer system 200 to access webservers 204, 206, and 208 via the network. Affiliate servers 204, 206,and 208 are also referred to as “web servers”, “network servers” and“sites” hosting content such as text and images for access by othercomputers on the network 202. An authentication server 210 is alsocoupled to network 202, facilitating communication between theauthentication server and client computer system 200 and authenticationservers 204, 206, and 208. Although referred to as an “authenticationserver”, authentication server 210 is also a web server capable ofinteracting with web browsers and other web servers. In this example,data is communicated between the authentication server 210, clientcomputer system 200, and web servers using http, a protocol commonlyused on the Internet to exchange information. An http specification ispublished by the Internet Engineering Task Force.

An authentication database 212 is coupled to authentication server 210.The authentication database 212 contains information necessary toauthenticate users and also identifies which elements of user profileinformation should be provided to a particular affiliate server when theuser accesses the affiliate server. Although the authentication database212 is shown separately from the authentication server 210, in otherembodiments of the invention, the authentication database is containedwithin the authentication server.

An authentication process authenticates a user of client computer 200seeking access to an affiliate server 204, 206, or 208. Theauthentication server 210 authenticates the user of client computer 200by requesting authenticating information, such as the user's login IDand password. If the user is successfully authenticated, thenauthentication server 210 generates an encrypted authentication ticketand communicates the ticket to the appropriate affiliate server. Theauthentication ticket indicates that the user is authenticated. Eachaffiliate server requires a key in order to decrypt the ticket and allowaccess by the user.

The authentication ticket contains two time stamps. The first time stampindicates the last time that the user's login ID and password werephysically typed by the user. The second time stamp indicates the lasttime that the user's login information was refreshed by theauthentication server. This “refresh” of the user's login informationcan be performed “silently” or by manual entry of the login information(i.e., login ID and password) by the user. The refreshing of the user'slogin information is performed by the authentication server. Oncecompleted, a new authentication ticket is issued to the affiliate serverindicating the new time stamp values.

The term “affiliate server” is defined herein as a web server that has“registered” or established a relationship or affiliation with theauthentication server 210. Each affiliate server 204, 206, and 208includes a code sequence that allows the affiliate server to communicatewith the authentication server 210 when a user (who is also registeredwith the authentication server) requests access to the affiliate server.

Prior to executing the authentication process, both the user of clientcomputer system 200 and the operator of affiliate server 204 “register”with the authentication server 210. This registration is a one-timeprocess which provides necessary information to the authenticationserver. The user of client computer system 200 registers by providinginformation such as the user's email address, password information, andvarious other information about the user or the client computer systemif desired. As part of the user registration process, the user isassigned (or selects) a login ID, which is a common login ID used toaccess any affiliate server. The login ID may also be referred to hereinas a “user name” or “login name”. Additionally, the user selects apassword associated with the login ID which is used for authenticationpurposes.

After registering and logging into the authentication server, the usercan visit any affiliate server (i.e., affiliate servers that are alsoregistered with the same authentication server) without requiring anyadditional authentication and without re-entering user information thatis already contained in the associated user profile.

The operator of affiliate server 204 registers with the authenticationserver 210 by providing information about the affiliate server (e.g.,server name and internet address). Additionally, the affiliate serverprovides information regarding its authentication requirements. Theauthentication requirements can be specified as the maximum time allowedsince the last login and entry of authentication information by the useras well as the maximum time allowed since the last “refresh” of theauthentication information by the user. Refreshing the authenticationinformation refers to the process of having the user re-enter thepassword to be certain that the appropriate user is still operating theclient computer system. This periodic refreshing of authenticationinformation is useful if the user leaves their computer system withoutlogging out of the authentication server, thereby allowing anotherindividual to access affiliate servers using the login ID of theprevious user. If a user requests access to the affiliate server afterthe maximum time allowed, then the user is re-authenticated (i.e.,refreshed) by the authentication server by issuing a new authenticationticket either silently or with required reentry of password as describedabove. Thus, although there is a central authentication server, eachindividual affiliate server can establish its own authenticationrequirements which are enforced by the authentication server. Afterregistering with the authentication server, the affiliate server can usethe authentication server to authenticate any user that has alsoregistered with the authentication server.

A block diagram showing the general operation of key generation anddistribution for decrypting tickets is provided in FIG. 3. Theauthentication server has several servers associated with it. A nexusserver 310 manages a configuration file, which contains informationregarding partner sites in the form of a partner.xml, information aboutkeys in a keys.xml, and information about the network server in anetworkserver.xml in the configuration file. These XML files are each acomponent configuration document (CCD). Further associated serversinclude a login server, which provide login services, a register server,and a logout server. Each of these servers may be integrated into asingle server, or comprise multiple servers themselves.

A key generator 345 is also associated with the authentication server.It has an administrative interface 350 that allows selection of new keysby a user, and provides keys in the form of an executable piece of codereferred to as key.exe via a network 360 (shown in two places forconvenience) such as the Internet, to one or more affiliate servers suchas a partner site 370. Partner site 370 may have several serversoperating as indicated in FIG. 3, all servicing the same network domain.The key generator also provides the keys.xml information to the nexus,where it is stored in the configuration file.

When a new partner site is registered by use of the register server 330,a key is generated for the site and provided by S-MIME secure encryptedemail, using standard certification, or physically mailed to operatorsof the site for installation. The key is delivered as an EXE with keydata embedded within it. An object, such as a COM object handlesinstallation and encryption of the keys. The first key has a versionnumber, such as “1”, and is stored by the site in encrypted form in aregistry using a piece of information that is specific to the physicalmachine, such as the MAC address of the first network card. The key.exeis used for decrypting tickets while the authentication server is stillrunning.

The administrative interface 350 is used to cause generation of a newsiteID for the new partner site, and generation of the key for that sitewith a one digit Hex version tag or number of “1”. Other lengths ofversion numbers may used as desired. Interface 350 updates the nexusserver 310 with information about the partner, such as site ID, keys.xmland current version number. Since there may be multiple trusted servers,i.e.: login servers, each is then triggered to refresh configurationinformation from the nexus server 310, including the new keys.xml filewith the new site's key version “1” included. The keys are distributedas a distinct private secure CCD in clear text over a highly secure(128-bit SSL) channel that is both client and server authenticated. Eachtime the CCD is retrieved by a trusted server, all the keys areimmediately encrypted and stored in a registry, and then the CCD iscompletely thrown away.

When a new key is to be updated, telephone or email is used to initiatethe generation of a new key. Such generation could also be automated ifdesired. The key may be updated on a regular schedule or variableschedule when initiated on the authentication server side, or may beinitiated in accordance with various security protocols on either theauthentication server side or partner site side. The partner siteadministrators may request a new key when an employee leaves, or anytime desired.

A new key is then generated at 345 and is updated on the nexus server310 to add the new key to a list of keys for the partner's siteID in theconfiguration file. The version number is incremented. When it reaches“F”, it loops back to one and resumes incrementing over time.

Key generator 345 also generates a key.exe file that can be installed onthe partner site servers. The new key.exe file is sent securely to thepartner and received. The key.exe file is then run against all serverson the partner site with an “/addkey” parameter that installs the newkey onto the server while still running. It is added as an additionalkey with no expiration date.

Next, the partner site runs the key.exe file against all servers with a“/makecurrent” parameter to make the new key the current key byswitching a registry key referred to as keycurrent to the new keyversion. The registry may also take the form of a config file, or anyfile in other systems. It also sets an expiration date on the previouscurrent key equal to the current time plus a registry key value referredto as TimeWindow. Time window may be set equal to the reauthorizationtime, or any other desired time. It may also be set to zero toimmediately begin exclusive use of the new current key to access thepartner site. If no time window has been set, old keys are flushed every24 hours or so if desired.

Key.exe may also be run against all servers using an “/expire” parameterprior to receiving a new key to cause a service interruption until newkeys are installed. This ensures that no new tickets using an oldcompromised key are accepted, and the old key can be immediately deletedfrom all servers.

The manager at each site 370 uses several registry keys to keep track ofencryption keys. A SiteID is the partner site's ID and is used in allcalls to the authentication server. A TimeWindow is essentially thesite's default preference for how “fresh” a user's ticket must be beforethey are redirected back to the login server for a new key. KeyDatacontains the actual keys, encrypted in the HMAC of the machine. Eachencryption key is stored as a value of this registry key, with theversion stamp as the value's name, and the encrypted key data as thevalue's data. These values map one to one with values under KeyTimes.KeyTimes specifies the expiration dates of all the keys referenced inKeyData. For each encryption key, this registry key will contain a valuewhose name is the encryption key's version stamp, and whose data is thedate and time at which this key is no longer valid. The value “−1 ”signifies that the key never expires. Typically, keys are set to neverexpire until it is time to update the key. CurrentKey is the versionstamp of the current key. The version stamp is referenced in allrequests to authentication servers. It indicates which key this serverexpects to get new tickets in.

When there is a new key, users that are currently logged on will be ableto continue their session using the old key. When KeyTimes expires, theymust use the new key to reauthorize their session. When this happens, orwhen a new user attempts to log in with an older version ticket afterkey.exe has been run with MakeCurrent, the partner site receives anattempt to log in by the user using the old ticket. When parsing aticket with an expired key, it is rejected, the user gets redirected tothe login server URL with parameters “ID=xxx&KV=2” used to specify thenew encryption key. The user is redirected by this URL to the loginserver. This redirection causes the login server to update theconfiguration file to indicate that the new key is now the current key.

A new ticket is generated using the new key. As each new user orreauthorization request is received for that site, the new current keywill be used to generate the ticket. In its unencrypted form, the ticketsent by the user comprises authentication time stamps and userinformation. When encrypted, it takes the form of: “keyversion#,string”, where the string is an encrypted form of the timestamps anduser information.

CONCLUSION

The key generation and distribution process provides a safe, reliableway of distributing keys to partner sites that requires minimal humanintervention, little if any user disruption, and minimal operationaldisruption. While parts of the process have been described in terms ofhuman operations, these operations may be easily automated. In the samemanner, automated operations may also be performed by human actions. Theprocess allows two keys to be operative for a desired amount of time.

1. A method, comprising: receiving, by an authentication server,authentication information of a user; encrypting, by the authenticationserver, a first ticket including the authentication information with afirst key of a first affiliated server, the first affiliated serverhaving first authentication requirements; encrypting, by theauthentication server, a second ticket including the authenticationinformation with a second key of a second affiliated server, the secondaffiliated server having second authentication requirements that aredifferent from the first authentication requirements; providing, by theauthentication server, the first ticket to the first affiliated serverto authenticate the user to the first affiliated server; providing, bythe authentication server, the second ticket to the second affiliatedserver to authenticate the user to the second affiliated server;refreshing the authentication information of the user, wherein the firstticket and the second ticket each include: (1) a first timestampcorresponding to when the user last manually entered the authenticationinformation and (2) a second timestamp corresponding to when theauthentication server last refreshed the authentication information ofthe user; generating a third key to replace the first key as a currentkey for the first affiliated server, the first key and the third keybeing concurrently valid for the first affiliated server for acoexistence period, wherein the first key and the second key eachinclude key data and executable code for decrypting the first ticket andthe second ticket, respectively; encrypting the first ticket with thethird key; and providing the first ticket encrypted with the third keyto the first affiliated server to re-authenticate the user to the firstaffiliated server without requiring the user to reenter theauthentication information to the authentication server.
 2. The methodof claim 1, wherein the refreshing comprises silently refreshing theauthentication information of the user.
 3. The method of claim 2,wherein the first and second authentication requirements each includeeither a maximum time since a last logon and entry of authenticationinformation by the user or a maximum time since a refresh of theauthentication information.
 4. The method of claim 1, wherein therefreshing comprises refreshing the authentication information of theuser including requiring the user to manually re-enter at least a partof the authentication information.
 5. The method of claim 1, furthercomprising setting a time for the first key when the first key is nolonger accepted by the first affiliated server, wherein the time is setto a reauthorization time determined by the first affiliated server. 6.The method of claim 1, wherein each key is encrypted for decoding at oneaffiliated server.
 7. The method of claim 1, further comprisinggenerating a configuration file to track keys for each affiliatedserver.
 8. The method of claim 1, wherein the keys are encrypted using ahardware address.
 9. An article of manufacture, comprising:computer-readable non transitory storage media; and a plurality ofexecutable instructions stored on the computer-readable non transitorystorage media which, when executed by an authentication server, case theauthentication server to: receive authentication information of a user;encrypt a first ticket including the authentication information with afirst key of a first affiliated server, the first affiliated serverhaving first authentication requirements; encrypt a second ticketincluding the authentication information with a second key of a secondaffiliated server, the second affiliated server having secondauthentication requirements that are different from the firstauthentication requirements; provide the first ticket to the firstaffiliated server to authenticate the user to the first affiliatedserver; provide the second ticket to the second affiliated server toauthenticate the user to the second affiliated server; refresh theauthentication information of the user, wherein the first ticket and thesecond ticket each include: (1) a first timestamp corresponding to whenthe user last manually entered the authentication information and (2) asecond timestamp corresponding to when the authentication server lastrefreshed the authentication information of the user; generate a thirdkey to replace the first key as a current key for the first affiliatedserver, the first key and the third key being concurrently valid for thefirst affiliated server for a coexistence period, wherein the first keyand the second key each include key data and executable code fordecrypting the first ticket and the second ticket, respectively; encryptthe first ticket with the third key; and provide the first ticketencrypted with the third key to the first affiliated server tore-authenticate the user to the first affiliated server withoutrequiring the user to reenter the authentication information to theauthentication server.
 10. The article of claim 9, wherein the refreshthe authentication information of the user comprises silently refreshingthe authentication information of the user.
 11. The article of claim 9,wherein the refresh the authentication information of the user comprisesrequiring the user to manually re-enter at least a part of theauthentication information.
 12. The article of claim 9, wherein theinstructions, when executed, further cause the authentication server toset a time for the first key when the first key is no longer accepted bythe first affiliated server, wherein the time is set to areauthorization time determined by the first affiliated server.
 13. Anauthentication server, comprising: a processor; and logic configured tobe operated by the processor to perform operations including: receivingauthentication information of a user; encrypting a first ticketincluding the authentication information with a first key of a firstaffiliated server, the first affiliated server having firstauthentication requirements; encrypting a second ticket including theauthentication information with a second key of a second affiliatedserver, the second affiliated server having second authenticationrequirements that are different from the first authenticationrequirements, wherein the first ticket and the second ticket eachinclude: (1) a first timestamp corresponding to when the user lastmanually entered the authentication information and (2) a secondtimestamp corresponding to when the authentication server last refreshedthe authentication information of the user; providing the first ticketto the first affiliated server to authenticate the user to the firstaffiliated server; providing the second ticket to the second affiliatedserver to authenticate the user to the second affiliated server;generating a third key to replace the first key as a current key for thefirst affiliated server, the first key and the third key beingconcurrently valid for the first affiliated server for a coexistenceperiod, wherein the first key and the second key each include key dataand executable code for decrypting the first ticket and the secondticket, respectively; encrypting the first ticket with the third key;and providing the first ticket encrypted with the third key to the firstaffiliated server to re-authenticate the user to the first affiliatedserver without requiring the user to reenter the authenticationinformation to the authentication server.
 14. The authentication serverof claim 13, wherein the first and second authentication requirementseach include either a maximum time allowed since a last manual entry ofthe authentication information or a maximum time since a last refresh ofthe authentication information.